Conversation
|
I really suggest to use it with natecraddock/workspaces.nvim#29 . LSP workspace folders is just hell. I improved the commit a bit. but would like to hear from you before investing more time in publishing this. Just want to make sure the general tendency is to include this after fixes. |
|
Hey @eyalk11, thanks for your contribution! I think Jedi provides a better way to extract workspace symbols than doing it file by file, which seems inefficient. Besides that, your work is also missing tests. |
|
What is the better method? I mean I suppose it doesn't parse all the files by default. |
|
i'd like to help with this, but i'm reading jedi docs and i can't find any included method to extract workspace symbols, only getting names from a singular script. @ccordoba12 could you clarify what exactly you meant here? |
|
@feakuru, you can take a look at what jedi-language-server does. If I'm not mistaken, they implemented getting workspace symbols the right way with Jedi. |
3 participants
It simply works. (
Telescope lsp_workspace_symbols)The only comment is that the formatting of document.path and d.module_path was different (don't know why the hell) -
(C:\... vs uri or \...) , so I used the full path for telescope to handle this.